Skip to content

[Fix] Fast replies to ambient participant conversations - #1459

Merged
roomote-roomote[bot] merged 9 commits into
developfrom
fix/fast-multi-user-responses-20m1xglvlsreh
Aug 28, 2026
Merged

[Fix] Fast replies to ambient participant conversations#1459
roomote-roomote[bot] merged 9 commits into
developfrom
fix/fast-multi-user-responses-20m1xglvlsreh

Conversation

@roomote-roomote

@roomote-roomote roomote-roomote Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

​Opened on behalf of @daniel-lxs. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

  • Keeps the shared Slack and Discord unmentioned-thread evaluator as the ingress gate, including the open Fast-conversation behavior from [Fix] Roomote ignores new participants in Fast threads #1444 and its interjection safeguards.
  • Reuses the existing native ignore_event action for an eligible unmentioned human turn after another person has participated, instead of adding a second ignore tool.
  • Authorizes ignore_event independently by turn context: optional platform events and eligible ambient human messages may close silently, while required platform events and directed human turns cannot.
  • Requires normal responses for explicit Fast commands, bot mentions, Slack direct and multi-person DMs, Discord DMs, new Fast conversations, and native Discord replies to Roomote.
  • Covers prompt guidance, native-tool authorization, optional and required platform events, Slack and Discord participant detection, DM safety, evaluator continuity, and Discord reply routing with focused regression tests.

Why this change was made

Fast conversations can include discussion between several people, but every evaluator-eligible message previously forced Roomote to respond. The current Fast lifecycle already has a source-independent native ignore action, so ambient human turns should reuse that capability rather than expand the tool catalog.

Impact

Roomote may stay silent when an eligible Fast turn is ambient conversation between people, without weakening participant eligibility or suppressing messages actually directed at Roomote. The native runtime rejects silent closure outside that narrow context. Browser proof is not applicable because the change affects ingress routing, tool authorization, and prompt behavior rather than rendered UI.

@roomote-community

roomote-community Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

No code issues found. See task

  • Preserve <replying_to> context for directed Fast turns in shared threads.
  • Preserve responses to native Discord replies to Roomote in shared Fast threads.

Reviewed d058755

Comment thread packages/cloud-agents/src/server/fast-agent/fast-agent-service.ts Outdated
Comment thread apps/api/src/handlers/discord/index.ts Outdated
@roomote-roomote roomote-roomote Bot changed the title [Fix] Fast mode replies to ambient participant conversation [Fix] Fast replies to ambient participant conversations Aug 28, 2026
@roomote-roomote
roomote-roomote Bot marked this pull request as ready for review August 28, 2026 21:03
@daniel-lxs daniel-lxs closed this Aug 28, 2026
@daniel-lxs daniel-lxs reopened this Aug 28, 2026
@roomote-roomote
roomote-roomote Bot merged commit d695335 into develop Aug 28, 2026
29 checks passed
@roomote-roomote
roomote-roomote Bot deleted the fix/fast-multi-user-responses-20m1xglvlsreh branch August 28, 2026 23:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant